System and method for LBA-based RAID

ABSTRACT

A system and method for an LBA RAID storage device. The LBA RAID storage device includes a plurality of data channels and a plurality of storage components. Each of the storage components is connected to one of the plurality of data channels. A storage controller is configured to receive a data and write the data to a RAID group made up of at least two storage components of the plurality of storage components that are each connected to a separate data channel.

CROSS-REFERENCE TO RELATED APPLICATION(S)

The present application claims priority to, and the benefit of U.S.Provisional Application No. 62/551,505, filed Aug. 29, 2017, U.S.Provisional Patent Application No. 62/621,450, filed on Jan. 24, 2018,the contents of which are incorporated herein by reference in itsentirety.

This application is also related to U.S. patent application Ser. No.15/832,681, filed on Dec. 5, 2017, the entire content of which isincorporated herein by reference.

BACKGROUND 1. Field

Some embodiments of the present disclosure relate generally to logicalblock address (LBA) based RAID in storage devices having multiplestorage components.

2. Description of the Related Art

SSD capacity has been steadily increasing since their introduction withmodern drives having storage capacity ranging from Gigabytes toTerabytes. As SSD sizes have increased, the potential losses associatedwith data corruption and drive failure have become a larger issue.Traditionally, Redundant Array of Independent Disks (RAID) has beenutilized to provide increased data protection and/or increased storageperformance. Common implementations of RAID include data striping acrossmultiple drives (RAID 0), data mirroring (RAID 1), and striping withparity (RAID 5 and RAID 6). Some RAID systems are implemented usingstatic physical page numbers (PPN) (e.g. physical NAND pages) forcalculating parity. However, using PPNs in SSDs is inefficient. A moreeffective method of utilizing RAID in SSDs is therefore needed.Furthermore, while each of the current RAID implementations offersvarying degrees of risk mitigation, implementing RAID requires multipledrives. In many applications, utilizing multiple drives is not anoption. Thus, a data protection mechanism similar to RAID that iscapable of being configured on a single drive is needed.

The above information is only for enhancement of understanding of thebackground of embodiments of the present disclosure, and therefore maycontain information that does not form the prior art.

SUMMARY

Some embodiments of the present disclosure provide a system and methodfor an LBA RAID storage device. In various embodiments, the LBA RAIDstorage device has a plurality of data channels and a plurality ofstorage components. In various embodiments, each of the plurality ofstorage components is connected to one of the plurality of datachannels. In various embodiments, the LBA RAID storage devices furtherincludes a storage controller, configured to receive a data and writethe data to a RAID group, the RAID group comprising at least two storagecomponents of the plurality of storage components each connected to aseparate data channel.

In various embodiments, the plurality of storage components compriseFlash memory chips.

In various embodiments, the RAID group has M storage components forreceiving the data and one parity storage component, where M is greaterthan 1.

In various embodiments, the RAID group has N storage components forreceiving the data and two parity storage components, where N is greaterthan one.

In various embodiments, the plurality of storage components include afirst storage component operating on a first data channel, a secondstorage component operating on a second data channel, a third storagecomponent operating on a third data channel, and a fourth storagecomponent operating on a forth data channel. In various embodiments, thestorage controller is further configured to stripe the data across thefirst storage component, the second storage component, and the thirdstorage component, calculate a parity for the data, and store the parityon the fourth storage component.

In various embodiments, striping the dataset across the first storagecomponent, the second storage component, and the third storage componentincludes writing a first dataset to a first logical block address (LBA)on the first storage component, writing a second dataset to a second LBAon the second storage component, and writing a third dataset to a thirdLBA on the third storage component.

In various embodiments, calculating the parity comprises calculating aparity based on the first LBA, the second LBA, and the third LBA.

In various embodiments, the parity is calculated by taking the exclusiveOR (XOR) of the first LBA, the second LBA, and the third LBA.

In various embodiments, the storage controller comprises aLBA-PPN-Parity Table and a Parity Group Table.

In various embodiments, the storage controller is further configured towrite the data to a RAID group according to the LBA-PPN-Parity Table andthe Parity Group Table.

In various embodiments, the storage controller is further configured toidentify a valid entry of a garbage collection erase block in theplurality of storage components, copy a candidate data from the garbagecollection erase block to a new physical address on the same storagecomponent of the plurality of storage components, and update theLBA-PPN-Parity Table with the new physical address.

In various embodiments, an LBA RAID storage device has multiple storagecomponents operating on multiple data channels. The LBA RAID storagedevice includes a first logical block address (LBA) on a first storagecomponent operating on a first data channel, a second LBA on a secondstorage component operating on a second data channel, a third LBA on athird storage component operating on a third data channel, a forth LBAon a fourth storage component operating on a forth data channel. Invarious embodiments, the LBA RAID storage device also includes a storagecontroller, configured to write a data to the first LBA, the second LBA,and the third LBA, calculate a parity for the data, and store the parityon the fourth LBA.

In various embodiments, the first storage component, the second storagecomponent, the third storage component, and the fourth storage componentare flash memory chips.

In various embodiments, writing the data comprises striping the dataacross the first LBA, the second LBA, and the third LBA.

In various embodiments, the parity is calculated by taking the exclusiveOR (XOR) of the first LBA, the second LBA, and the third LBA.

In various embodiments, the storage controller comprises aLBA-PPN-Parity Table and a Parity Group Table.

In various embodiments, the storage controller is further configured towrite the data to a RAID group according to the LBA-PPN-Parity Table andthe Parity Group Table.

In various embodiments, the storage controller is further configured toidentify a valid entry of a garbage collection erase block on the firstLBA, copy a candidate data from the first LBA to a new physical addresson the first storage component, and update the LBA-PPN-Parity Table withthe new physical address of the first LBA.

In various embodiments, a method of controlling a solid state diskincludes receiving a write request to store a data at a storagecontroller, writing the data to a first storage component operating on afirst data channel, a second storage component operating on a seconddata channel, and a third storage component operating on a third datachannel, and calculating a parity and store the parity in a fourthstorage component operating on a fourth data channel.

In various embodiments, writing the data includes writing the data to afirst logical block address (LBA) on the first storage component, asecond LBA on the second storage component, and a third LBA on the thirdstorage component.

In various embodiments, the method further includes mapping the writerequest to a RAID group according to a LBA-PPN-Parity Table and a ParityGroup Table stored on a firmware.

In various embodiments, calculating a parity includes taking theexclusive OR (XOR) of the first LBA, the second LBA, and the third LBA.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments can be understood in more detail from the followingdescription taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 depicts an example LBA-based RAID storage device in accordancewith various embodiments of the present invention;

FIG. 2 depicts an example of memory chips and data busses in a LBA-basedRAID storage device in accordance with various embodiments of thepresent invention;

FIG. 3 depicts a method of storing data in an LBA RAID storage device inaccordance with various embodiments of the present invention;

FIG. 4 depicts an LBA-based RAID group operating on an LBA RAID storagedevice in accordance with various embodiments of the present invention;

FIG. 5 depicts an example LBA-Physical Page Number (PPN)-Parity Tableaccording to various embodiments of the present invention;

FIG. 6 depicts an example Parity Table according to various embodimentsof the present invention.

DETAILED DESCRIPTION

Features of the inventive concept and methods of accomplishing the samemay be understood more readily by reference to the following detaileddescription of embodiments and the accompanying drawings. Hereinafter,embodiments will be described in more detail with reference to theaccompanying drawings, in which like reference numbers refer to likeelements throughout. The present invention, however, may be embodied invarious different forms, and should not be construed as being limited toonly the illustrated embodiments herein. Rather, these embodiments areprovided as examples so that this disclosure will be thorough andcomplete, and will fully convey the aspects and features of the presentinvention to those skilled in the art. Accordingly, processes, elements,and techniques that are not necessary to those having ordinary skill inthe art for a complete understanding of the aspects and features of thepresent invention may not be described. Unless otherwise noted, likereference numerals denote like elements throughout the attached drawingsand the written description, and thus, descriptions thereof will not berepeated. In the drawings, the relative sizes of elements, layers, andregions may be exaggerated for clarity.

In the following description, for the purposes of explanation, numerousspecific details are set forth to provide a thorough understanding ofvarious embodiments. It is apparent, however, that various embodimentsmay be practiced without these specific details or with one or moreequivalent arrangements. In other instances, well-known structures anddevices are shown in block diagram form in order to avoid unnecessarilyobscuring various embodiments.

It will be understood that when an element, layer, region, or componentis referred to as being “on,” “connected to,” or “coupled to” anotherelement, layer, region, or component, it can be directly on, connectedto, or coupled to the other element, layer, region, or component, or oneor more intervening elements, layers, regions, or components may bepresent. However, “directly connected/directly coupled” refers to onecomponent directly connecting or coupling another component without anintermediate component. Meanwhile, other expressions describingrelationships between components such as “between,” “immediatelybetween” or “adjacent to” and “directly adjacent to” may be construedsimilarly. In addition, it will also be understood that when an elementor layer is referred to as being “between” two elements or layers, itcan be the only element or layer between the two elements or layers, orone or more intervening elements or layers may also be present.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the presentinvention. As used herein, the singular forms “a” and “an” are intendedto include the plural forms as well, unless the context clearlyindicates otherwise. It will be further understood that the terms“comprises,” “comprising,” “have,” “having,” “includes,” and“including,” when used in this specification, specify the presence ofthe stated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof. As used herein, the term “and/or” includes anyand all combinations of one or more of the associated listed items.

As used herein, the term “substantially,” “about,” “approximately,” andsimilar terms are used as terms of approximation and not as terms ofdegree, and are intended to account for the inherent deviations inmeasured or calculated values that would be recognized by those ofordinary skill in the art. “About” or “approximately,” as used herein,is inclusive of the stated value and means within an acceptable range ofdeviation for the particular value as determined by one of ordinaryskill in the art, considering the measurement in question and the errorassociated with measurement of the particular quantity (i.e., thelimitations of the measurement system). For example, “about” may meanwithin one or more standard deviations, or within ±30%, 20%, 10%, 5% ofthe stated value. Further, the use of “may” when describing embodimentsof the present invention refers to “one or more embodiments of thepresent invention.” As used herein, the terms “use,” “using,” and “used”may be considered synonymous with the terms “utilize,” “utilizing,” and“utilized,” respectively. Also, the term “exemplary” is intended torefer to an example or illustration.

When a certain embodiment may be implemented differently, a specificprocess order may be performed differently from the described order. Forexample, two consecutively described processes may be performedsubstantially at the same time or performed in an order opposite to thedescribed order.

Various embodiments are described herein with reference to sectionalillustrations that are schematic illustrations of embodiments and/orintermediate structures. As such, variations from the shapes of theillustrations as a result, for example, of manufacturing techniquesand/or tolerances, are to be expected. Further, specific structural orfunctional descriptions disclosed herein are merely illustrative for thepurpose of describing embodiments according to the concept of thepresent disclosure. Thus, embodiments disclosed herein should not beconstrued as limited to the particular illustrated shapes of regions,but are to include deviations in shapes that result from, for instance,manufacturing. For example, an implanted region illustrated as arectangle will, typically, have rounded or curved features and/or agradient of implant concentration at its edges rather than a binarychange from implanted to non-implanted region. Likewise, a buried regionformed by implantation may result in some implantation in the regionbetween the buried region and the surface through which the implantationtakes place. Thus, the regions illustrated in the drawings are schematicin nature and their shapes are not intended to illustrate the actualshape of a region of a device and are not intended to be limiting.

The electronic or electric devices and/or any other relevant devices orcomponents according to embodiments of the present invention describedherein may be implemented utilizing any suitable hardware, firmware(e.g. an application-specific integrated circuit), software, or acombination of software, firmware, and hardware. For example, thevarious components of these devices may be formed on one integratedcircuit (IC) chip or on separate IC chips. Further, the variouscomponents of these devices may be implemented on a flexible printedcircuit film, a tape carrier package (TCP), a printed circuit board(PCB), or formed on one substrate. Further, the various components ofthese devices may be a process or thread, running on one or moreprocessors, in one or more computing devices, executing computer programinstructions and interacting with other system components for performingthe various functionalities described herein. The computer programinstructions are stored in a memory which may be implemented in acomputing device using a standard memory device, such as, for example, arandom access memory (RAM). The computer program instructions may alsobe stored in other non-transitory computer readable media such as, forexample, a CD-ROM, flash drive, or the like. Also, a person of skill inthe art should recognize that the functionality of various computingdevices may be combined or integrated into a single computing device, orthe functionality of a particular computing device may be distributedacross one or more other computing devices without departing from thespirit and scope of the exemplary embodiments of the present invention.

Unless otherwise defined, all terms (including technical and scientificterms) used herein have the same meaning as commonly understood by oneof ordinary skill in the art to which the present invention belongs. Itwill be further understood that terms, such as those defined in commonlyused dictionaries, should be interpreted as having a meaning that isconsistent with their meaning in the context of the relevant art and/orthe present specification, and should not be interpreted in an idealizedor overly formal sense, unless expressly so defined herein.

Embodiments of the present invention include a system and method forlogical block address (LBA) RAID. In various embodiments, the systemincludes a solid state drive (SSD) system having multiple flash memorychips operating on multiple data channels. In some examples, the flashmemory chips may be NAND memory chips. In various embodiments, the SSDmay be configured for LBA-based RAID by striping the data across flashchips operating on different channels. In various embodiments, a paritymay be added using additional chips on a different channel than the onesholding the data.

FIG. 1 depicts an example LBA-based RAID storage device in accordancewith various embodiments of the present invention.

Referring to FIG. 1, in various embodiments, the LBA RAID storage deviceutilizes a multiple memory component architecture to perform LBA-basedRAID operations within the LBA RAID storage device. For example, invarious embodiments, the LBA RAID storage device includes a storagecontroller 100 and a firmware 110 for controlling Input/Output (I/O)operations. The storage controller 100 receives I/O requests (e.g. adata) from a host (e.g. a host application) and processes them accordingto the RAID configuration stored on the firmware 110. In variousembodiments, the LBA RAID storage device includes persistent storage 120that includes a plurality of memory components. For example, thepersistent storage 120 may include multiple data channels 130, 140, 150and each data channel may include multiple memory chips 132-136,142-146, 152-156. In various embodiments the memory chips may includeany persistent memory chips. For example, the memory chips may includeflash memory chips (e.g. NAND), 3D XPoint, etc. In various embodimentsthe controller 100 and firmware 110 may be configured to utilizedifferent memory chips 132-136, 142-146, 152-156 operating on differentdata channels 130, 140, 150 to create a LBA RAID. For example, invarious embodiments, the LBA RAID may stripe data across multiple chipsand include parity bits on an additional chip. In another example, theLBA RAID may stripe data across multiple chips and utilizing twoadditional chips for parity bits. For example, the LBA RAID may beconfigured in a M data chips+1 parity (similar to RAID 5) or N datachips+2 parity (similar to RAID 6) where M and N are any number biggerthan one. Striping data across multiple chips operating on differentchannels may provide improve drive performance. For example, databottlenecks may be relieved since I/O from an array may be distributedacross multiple channels in the SSD.

FIG. 2 depicts an example of memory chips and data busses in a LBA-basedRAID storage device in accordance with various embodiments of thepresent invention.

Referring to FIG. 2, in various embodiments, a LBA RAID storage device200 may be configured to operate with a RAID system utilizing multipleflash memory chips. For example, the LBA RAID storage device 200includes a plurality of flash memory chips 201-216. In variousembodiments, each of the flash memory chips 201-216 may have a logicalblock address (LBA). In various embodiments, the plurality of flashmemory chips 201-216 may operate on multiple data channels 217-220. Forexample, a first plurality of flash memory chips 201, 205, 209, and 213may all operate on a first channel 217, a second plurality of flashmemory chips 202, 206, 210, and 214 may all operate on a second channel218, a third plurality of flash memory chips 203, 207, 211, and 215 mayall operate on a third channel 219, and a fourth plurality of flashmemory chips 204, 208, 212, and 216 may all operate on a fourth channel220.

In various embodiments, flash memory chips may be grouped into RAIDgroups. For example, the solid state disk (SSD) 200 may include a firstRAID array 230 having a first flash memory chip 201, a second flashmemory chip 202, a third flash memory chip 203, and a fourth flashmemory chip 204. Similarly, the SSD 200 may include a second RAID array240 having a fifth flash memory chip 205, a sixth flash memory chip 206,a seventh flash memory chip 207, and an eighth flash memory chip 208. Invarious embodiments, each of the RAID arrays 230, 240 may be configuredwith a parity chip. In some examples, the parity bits may be stored onflash memory chips on a different channel. For example, in variousembodiments, the flash chips 204, 208 (250) on the fourth channel 220may all be used for storing parity bits.

In various embodiments, parity data may be calculated based on LBAs. Forexample, in various embodiments, the first flash memory chip 201 mayhave an LBA of 1, the second flash memory chip 202, may have an LBA of2, and the third flash memory chip 203 may have an LBA of 3. The fourthflash memory chip 204 may be the parity value of LBA of 1 and LBA of 2and LBA of 3. Parity bits may be calculated in any manner consistentwith the type of parity being used (e.g. a single parity, a doubleparity, etc.) For example, in various embodiments, parity for a singleparity system may be calculated by taking the exclusive OR (XOR) of thedata stored in each of the LBAs in the RAID array (e.g. the parity bitsare calculated on a LBA basis). For example, in the first RAID group230, data may be striped (e.g. split between) across the first flashmemory chip 201, the second flash memory chip 202, and the third flashmemory chip 203 and parity bits may be calculated by taking the XOR ofthe data stored on first flash memory chip 201, the second flash memorychip 202, and the third flash memory chip 203, with the resulting paritybits being stored on the fourth flash memory chip 204 (e.g. data(LBA1)XOR data(LBA2) XOR data(LBA3)=parity data).

FIG. 3 depicts a method of storing data in an LBA RAID storage device inaccordance with various embodiments of the present invention. FIG. 4depicts an LBA-based RAID group operating on an LBA RAID storage devicein accordance with various embodiments of the present invention.

Referring to FIGS. 3 and 4, in various embodiments, the LBA RAID storagedevice may include a RAID group (e.g. a RAID array) 400. In variousembodiments, the RAID group 400 may be configured in a 3+1P scheme usinga first flash memory chip 410, a second flash memory chip 420 and athird flash memory chip 430 for storing the data and a fourth flashmemory chip 440 used for parity (e.g. in the configuration describedabove with reference to FIG. 2 where data is striped across 3 chips anda fourth chip is used as a parity). In various embodiments, each of theflash memory chips 410-440 may include a plurality of LBAs and performsRAID across the LBAs. For example, the LBA_i, LBA_j, LBA_k, and LBA_Pmay form a RAID array. In various embodiments, the NAND flash memorychips 410. 420, 430, 440 may be configured with 4 KB physical pages. Insome embodiments, data being written may be divided in to RAID elementchunks that are multiples of LBA sizes. For example, each LBA may be 512bytes. Thus, an element may be LBA-sized (512 bytes), 8 LBA-sized (4KB), 16 LBA-sized (8 KB), etc.

In various embodiments, the LBA RAID storage device receives a storagerequest to store a dataset from a host (e.g. an application) at thestorage controller (S300). In various embodiments, the storagecontroller may utilize a LBA-PPN-Parity Table and a Parity Group Tableto determine the appropriate location for storing the dataset and theassociated parity pits (e.g. LBA_i, LBA_j, LBA_k, and LBA_P) (S310). Forexample, in various embodiments, the storage request is to store thedataset on LBA_i. The storage controller references the LBA-PPN-Paritytable and determines the Parity Index for LBA_i is 1. The storagecontroller may then reference the Parity Table to determine the otherLBAs associated with the RAID group and writes to the group. Forexample, the storage controller maps the split the received dataset suchthat the first 4 kb of the dataset is written to LBA_i on the first chip410, the second 4 kb of dataset may then be written to LBA_j on thesecond chip 420 and so on (S320). The controller may then calculate theparity bits for the written data (e.g. by performing an XOR function)and store the parity bits on the parity LBA_P (S330) (as defined in theParity Table).

FIG. 5 depicts an example LBA-Physical Page Number (PPN)-Parity Tableaccording to various embodiments of the present invention. FIG. 6depicts an example Parity Table according to various embodiments of thepresent invention.

Referring to FIG. 5 and FIG. 6 the LBA RAID storage device may include aLBA-PPN-Parity Table 500 and a Parity Table 600 for maintaining datalocations, RAID arrays, and parity information. In various embodimentsthe LBA-PPN-Parity Table 500 and the Parity Table 600 may be stored inthe storage device's firmware and updated by the storage controller. Invarious embodiments, the LBA-PPN-Parity Table 500 and Parity Table 600are configured to define and map the various RAID arrays on the LBA RAIDstorage device. For example, the LBA-PPN-Parity Table 500 and the ParityTable 600 may define which LBAs form an array and the location of theparity data for each array.

In various embodiments, the LBA-PPN-Parity Table 500 is configured tomap LBAs to PPNs and to a parity index. For example, in variousembodiments, the LBA-PPN-Parity Table 500 includes an LBA index 510, anassociated PPN 520, and an associated parity index 530.

In various embodiments, the Parity Table 600 is configured to definewhich LBAs are associated with which parity LBAs or PPN. For example,the Parity Table 600 includes a parity index 610 that maps to the parityindex 530 from the LBA-PPN-Parity Table 500. Associated with each parityindex 610 is each LBA 620, 630, 640 with a Parity PPN 650. For example,as shown in, the LBA-PPN-Parity Table 500, LBA_i, LBA_j, and LBA_k areeach associated with the parity index 1. Thus, anytime the data onLBA_i, LBA_j, and LBA_k is modified, the parity P1 is also updated. Forexample, in various embodiments, when data is updated (e.g. data on atleast one of the LBA's of an array is changed), the corresponding parityis also recalculated using an XOR function and the associated PPNs theLBA-PPN-Parity Table 500 and the Parity Table 600 (e.g. the PPN 520 andthe Parity PPN 650) are also updated.

In various embodiments, data may be deleted from an LBA in the LBA RAIDstorage device. For example, in various embodiments, the LBA data may beremoved from the parity by XORing the LBA data with the parity. Theupdated parity may then be stored to a new PPN. The previous PPN andparity index in the LBA-PPN-Parity Table 500 may be deleted. The LBA maythen be removed from the Parity Table 600. In some cases, all of theLBAs may have been deleted from a raid array. In the case of all of theLBAs being deleted from one RAID array, the corresponding parity entry(e.g. all the entries associated with a parity index 610) may be deletedfrom the Parity Table 600.

In various embodiments, the LBA RAID storage device is configured forintra-chip level garbage collection and wear leveling. For example, whena valid data is copied to a new erase block during the garbagecollection or wear leveling process, the new erase block may beallocated from the same flash memory chip. For example, LBA_i may be avalid entry of a garbage collection candidate erase block (or wearleveling block) in a flash memory chip x and thus the data in LBA_ineeds to be copied to a new erase block. In various embodiments, the newerase block will be allocated in the same flash memory chip x. In thesecases, the PPN 520 from the LBA-PPN-Parity Table 500 is updated and noupdate to the Parity Table 600 is needed (unless the data being moved isparity data).

Accordingly, the above described embodiments of the present disclosureprovide a system and method for LBA-based RAID storage devices. Invarious embodiments, the LBA RAID storage devices have multiplecomponents such as NAND memory chips (e.g. Flash memory chips) that canbe used to perform RAID within a SSD offering improvements in dataprotection and performance. In various embodiments, a LBA-PPN-ParityTable and Parity Group Table are used for mapping the locations of dataand associated parity bits.

The foregoing is illustrative of example embodiments, and is not to beconstrued as limiting thereof. Although a few example embodiments havebeen described, those skilled in the art will readily appreciate thatmany modifications are possible in the example embodiments withoutmaterially departing from the novel teachings and advantages of exampleembodiments. Accordingly, all such modifications are intended to beincluded within the scope of example embodiments as defined in theclaims. In the claims, means-plus-function clauses are intended to coverthe structures described herein as performing the recited function andnot only structural equivalents but also equivalent structures.Therefore, it is to be understood that the foregoing is illustrative ofexample embodiments and is not to be construed as limited to thespecific embodiments disclosed, and that modifications to the disclosedexample embodiments, as well as other example embodiments, are intendedto be included within the scope of the appended claims. The inventiveconcept is defined by the following claims, with equivalents of theclaims to be included therein.

What is claimed is:
 1. A logical block address (LBA) redundant array ofindependent disks (RAID) storage device comprising: a plurality of datachannels; a plurality of storage components for storing data to the RAIDstorage device, wherein each of the plurality of storage components isconnected to one of the plurality of data channels; a storage controllerconfigured to receive data associated with an LBA and write the data toa RAID group, the RAID group comprising at least two storage componentsof the plurality of storage components each connected to a separate datachannel, wherein the storage controller is further configured to:receive a storage request for the data; determine a parity indexassociated with the LBA; identify the RAID group associated with theparity index, wherein the storage controller comprises a first table anda second table, wherein the first table comprises an LBA index and aparity index, and the second table comprises LBAs and correspondingparity bits, and write the data to the RAID group based on the firsttable and the second table.
 2. The LBA RAID storage device of claim 1,wherein the plurality of storage components comprises flash memorychips.
 3. The LBA RAID storage device of claim 1, wherein the RAID groupcomprises M storage components for receiving the data and one paritystorage component, where M is an integer greater than
 1. 4. The LBA RAIDstorage device of claim 1, wherein the RAID group comprises N storagecomponents for receiving the data and two parity storage components,where N is an integer greater than one.
 5. The LBA RAID storage deviceof claim 1, wherein: the plurality of storage components comprises afirst storage component operating on a first data channel, a secondstorage component operating on a second data channel, a third storagecomponent operating on a third data channel, and a fourth storagecomponent operating on a forth data channel; the storage controller isfurther configured to: stripe the data across the first storagecomponent, the second storage component, and the third storagecomponent; calculate a parity for the data; and store the parity on thefourth storage component.
 6. The LBA RAID storage device of claim 5,wherein striping the data across the first storage component, the secondstorage component, and the third storage component comprises: writing afirst dataset to a first LBA on the first storage component; writing asecond dataset to a second LBA on the second storage component; andwriting a third dataset to a third LBA on the third storage component.7. The LBA RAID storage device of claim 6, wherein calculating theparity comprises calculating a parity based on the first LBA, the secondLBA, and the third LBA.
 8. The LBA RAID storage device of claim 7,wherein the parity is calculated by taking an exclusive OR (XOR) of thefirst LBA, the second LBA, and the third LBA.
 9. The LBA RAID storagedevice of claim 1, wherein the first table comprises a LBA-physical pagenumbers (PPN)-Parity Table and the second table comprises a Parity GroupTable.
 10. The LBA RAID storage device of claim 9, wherein the storagecontroller is further configured to write the data to the RAID groupaccording to the LBA-PPN-Parity Table and the Parity Group Table. 11.The LBA RAID storage device of claim 9, wherein the storage controlleris further configured to: identify a valid entry of a garbage collectionerase block in the plurality of storage components; copy a candidatedata from the garbage collection erase block to a new physical addresson the same storage component of the plurality of storage components;and update the LBA-PPN-Parity Table with the new physical address.
 12. Alogical block address (LBA) redundant array of independent disks (RAID)storage device comprising: a first logical block address (LBA) on afirst storage component operating on a first data channel, the firststorage component to store data to the RAID storage device; a second LBAon a second storage component operating on a second data channel, thesecond storage component to store data to the RAID storage device; athird LBA on a third storage component operating on a third datachannel, the third storage component to store data to the RAID storagedevice; a fourth LBA on a fourth storage component operating on a forthdata channel; and a storage controller configured to: write data to thefirst LBA, the second LBA, and the third LBA; calculate a parity for thedata; and store the parity on the fourth LBA, wherein the storagecontroller comprises a first table and a second table, wherein the firsttable comprises an LBA index and a parity index, and the second tablecomprises LBAs and corresponding parity bits, wherein the storagecontroller is configured to write the data to the first LBA, the secondLBA, and the third LBA, based on the first table and the second table.13. The LBA RAID storage device of claim 12, wherein the first storagecomponent, the second storage component, the third storage component,and the fourth storage component comprise flash memory chips.
 14. TheLBA RAID storage device of claim 12, wherein writing the data comprisesstriping the data across the first LBA, the second LBA, and the thirdLBA.
 15. The LBA RAID storage device of claim 12, wherein the parity iscalculated by taking an exclusive OR (XOR) of the first LBA, the secondLBA, and the third LBA.
 16. The LBA RAID storage device of claim 12,wherein the first table comprises a LBA-physical page numbers(PPN)-Parity Table and the second table comprises a Parity Group Table.17. The LBA RAID storage device of claim 16, wherein the storagecontroller is further configured to write the data to a RAID groupaccording to the LBA-PPN-Parity Table and the Parity Group Table. 18.The LBA RAID storage device of claim 16, wherein the storage controlleris further configured to: identify a valid entry of a garbage collectionerase block on the first LBA; copy a candidate data from the first LBAto a new physical address on the first storage component; and update theLBA-PPN-Parity Table with the new physical address of the first LBA. 19.A method of controlling a solid state disk comprising: receiving a writerequest to store a data at a storage controller; writing the data to afirst storage component operating on a first data channel, a secondstorage component operating on a second data channel, and a thirdstorage component operating on a third data channel; and calculating aparity and store the parity in a fourth storage component operating on afourth data channel, wherein the storage controller comprises a firsttable and a second table, wherein the first table comprises a logicalblock address (LBA) index and a parity index, and the second tablecomprises LBAs and corresponding parity bits, wherein the storagecontroller is configured to write the data to the first storagecomponent, the second storage component, and the third storagecomponent, based on the first table and the second table.
 20. The methodof controlling the solid state disk of claim 19, wherein writing thedata comprises writing the data to a first logical block address (LBA)on the first storage component, a second LBA on the second storagecomponent, and a third LBA on the third storage component, wherein thefirst table comprises a LBA-physical page numbers (PPN)-Parity Table andthe second table comprises a Parity Group Table.
 21. The method ofcontrolling the solid state disk of claim 20, further comprising:mapping the write request to a redundant array of independent disks(RAID) group according to the LBA-PPN-Parity Table and the Parity GroupTable stored on a firmware.
 22. The method of controlling the solidstate disk of claim 20, wherein calculating a parity comprises taking anexclusive OR (XOR) of the first LBA, the second LBA, and the third LBA.